Language input correction

ABSTRACT

The present disclosure generally relates to language input correction. In one example process, a sequence of contact inputs can be detected via a keyboard interface on a touch-sensitive display. A contact input of the sequence of contact inputs can include a contact motion from a first position to a second position of the keyboard interface. A plurality of candidate words corresponding to the sequence of contact inputs can be determined. The plurality of candidate words can be ranked based on a probability that the contact input is an intended input to select a first key of the keyboard interface, and a probability that the contact input is an intended input to select a second key of the keyboard interface. A portion of the plurality of candidate words can be displayed for user selection.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from U.S. Provisional Ser. No.62/171,911, filed on Jun. 5, 2015, entitled LANGUAGE INPUT CORRECTION,which is hereby incorporated by reference in its entirety for allpurposes.

FIELD

The present disclosure relates generally to language input, and morespecifically to techniques for language input correction.

BACKGROUND

Various keyboard interfaces can be provided to enable users to entertext or other content elements into application documents, such as wordprocessing documents, messages, or emails. For example, intouch-interface mobile devices, a keyboard interface can be displayedvia a touch-sensitive display. User touch inputs can be processed todetermine which keys were intended to be inputted by the user andcorresponding characters associated with the intended keys can bedisplayed in a text field.

Due to physical limitations (e.g., size) of keyboard interfaces onmobile devices, touch inputs from a user can be determined to correspondto keys that the user did not intend to input. This can bring aboutsignificant inaccuracy and inefficiency when inputting text. Further,for languages that rely on converting phonetic-based inputs (e.g.,Chinese pinyin, Japanese hiragana, etc.) into predicted candidate text(e.g., Chinese characters, Japanese words, etc.), errors in text inputcan result in the generation of a large number of irrelevant candidates.This can significantly compromise user experience and productivity.

BRIEF SUMMARY

Systems and processes for language input correction are provided. In oneexample process, a sequence of contact inputs can be detected via akeyboard interface on a touch-sensitive display. A contact input of thesequence of contact inputs can include a contact motion from a firstposition to a second position of the keyboard interface. A plurality ofcandidate words corresponding to the sequence of contact inputs can bedetermined. The plurality of candidate words can be ranked based on aprobability that the contact input is an intended input to select afirst key of the keyboard interface, and a probability that the contactinput is an intended input to select a second key of the keyboardinterface. A portion of the plurality of candidate words can bedisplayed for user selection.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-C are screenshots of an electronic device illustrating anexemplary reduced keyboard interface in accordance with someembodiments.

FIG. 7 is a flow diagram illustrating an exemplary process for languageinput correction in accordance with some embodiments.

FIGS. 8A-D are exemplary screenshots of an electronic deviceillustrating various stages of an exemplary process for language inputcorrection in accordance with some embodiments.

FIG. 9 is a functional block diagram illustrating an exemplaryelectronic device in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

The present disclosure generally relates to systems and processes forlanguage input correction. In an exemplary process, a sequence ofcontact inputs can be detected via a keyboard interface on atouch-sensitive display. A contact input of the sequence of contactinputs can include a contact motion from a first position to a secondposition of the keyboard interface. A plurality of candidate wordscorresponding to the sequence of contact inputs can be determined. Theplurality of candidate words can be ranked based on a probability thatthe contact input is an intended input to select a first key of thekeyboard interface, and a probability that the contact input is anintended input to select a second key of the keyboard interface. Aportion of the plurality of candidate words can be displayed for userselection. By considering more than one key of the keyboard interface asthe intended input of the contact input, the process can determine anddisplay candidate words that more accurately reflect the user's intent.Further, the process can correct for unintended contact inputs (e.g.,typos) by considering other possible intended keys, thereby increasingthe relevancy of displayed candidate words. This can improve theaccuracy and productivity for inputting text.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

1. Exemplary Devices for Performing Language Input Correction

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. The computer-readable storage medium may storeinstructions for performing process 700, described below. Memory 102 mayinclude high-speed random access memory and may also includenon-volatile memory, such as one or more magnetic disk storage devices,flash memory devices, or other non-volatile solid-state memory devices.Memory controller 122 may control access to memory 102 by othercomponents of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in L/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input). For example, text input module 134 can includeinstructions for providing keyboard interface 800 describe below withreference to FIGS. 8A-8D. Additionally, text input module 134 caninclude instructions for performing process 700, described below. Inparticular, text input module 134 can include one or more geometrymodels and one or more language models, described below, for languageinput correction.

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134. GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to 1/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described below, including process 700 (e.g., FIG. 7). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Forpurposes of this document, a “non-transitory computer-readable storagemedium” can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

2. Reduced Keyboard Interface

Reduced keyboard interfaces can be used to provide text input onelectronic devices (e.g., devices 100, 300, or 500). FIGS. 6A-Cillustrate exemplary reduced keyboard interface 600 for inputtingJapanese text. Reduced keyboard interface 600 can be referred to as a10-key kana keyboard interface. Reduced keyboard interface 600 can bedisplayed on a touch screen (e.g., touch screen 112) of the electronicdevice. As shown, reduced keyboard interface 600 can include 10 primarycharacter keys 602 (e.g., labelled

,

,

,

,

,

,

,

,

, and

) for inputting Japanese hiragana characters and 2 additional keys 604,606 for adding diacritic symbols and punctuation, respectively. Eachprimary character key 602 can be configured to provide access to one ormore secondary character keys. In particular, as shown in FIG. 6B,providing a touch contact to primary character key 602-1 associated withthe character

an cause four secondary character keys 608, 610, 612, 614 associatedwith the characters

,

,

,

, respectively, to be displayed. As such, in the present example, 50character keys can be available for input via the 10 primary characterkeys 602.

Reduced keyboard interface 600 can be configured to receive contactinputs from a user and cause respective hiragana characters to beinputted to the device. For inputting hiragana characters associatedwith primary character keys 602, a single-tap input can be provided tothe respective primary character key 602. For example, with reference toFIG. 6B, a single-tap input can be provided to primary character key602-1 to input the character

. A single-tap input can include a touch contact to a primary characterkey followed by a release or break in contact from the primary characterkey. In addition, lateral movement during the touch contact can be lessthan a predetermined threshold amount.

For inputting hiragana characters associated with secondary characterkeys, a flick input can be provided to the respective primary characterkey 602. For example, as shown in FIGS. 6B-C, a flick input in a firstdirection (e.g., a direction represented by arrow 616) can be providedto primary character key 602-1 and to input the character

via secondary character key 608. As shown in FIG. 6C, in response to theflick input, reduced keyboard interface 600 can highlight secondarycharacter key 608 to indicate that input of the characterr

is received via secondary character key 608. The flick input can includea contact motion from first position 617 (e.g., at primary character key602-1) to second position 619 (e.g., at secondary character key 608) onthe reduced keyboard interface 600. In particular, in the presentexample, the flick input can include initiating a touch contact toprimary character key 602-1 at first position 617, providing a contactmotion from first position 617 to second position 619, and releasingtouch contact at second position 619 from secondary character key 608.The flick input can be provided such that there is no break in contactwith reduced language input interface 600 from the initial touch contactto the release in touch contact.

Hiragana characters associated with secondary character keys canalternatively be inputted by providing a multi-tap input to therespective primary character key 602. In particular, each secondarycharacter key can be associated with a predefined multi-tap inputpattern. For example, to input the character

, a predefined multi-tap input pattern that includes a first touchcontact to primary character key 602-1 followed by a second touchcontact to character key 602-1 can be received (e.g., double-tap input).A break or release in touch contact can occur between the first touchcontact and the second touch contact. Further, the first touch contactand the second touch contact can occur within a predetermined amount oftime. In a similar manner, the character

can be inputted with a predefined multi-tap input pattern that includesthree touch contacts to primary character key 602-1 (e.g., triple-tapinput).

Although in the present example, reduced keyboard interface 600 isconfigured to input Japanese text, it should be recognized that in otherexamples, the reduced keyboard interface can be configured to input textof other languages. In particular, each primary character key andsecondary character key can correspond to a written symbol of alanguage. Further, it should be appreciated that the number of primarycharacter keys and the number of secondary character keys that can beaccessed via each primary character key can vary.

3. Processes for Language Input Correction

FIG. 7 is a flow diagram illustrating process 700 for language inputcorrection according to various examples. FIGS. 8A-D are exemplaryscreenshots of an electronic device illustrating various stages of anexemplary process for language input correction according to variousexamples. Process 700 can be performed at a device (e.g., device 100,300, or 500) with a touch-sensitive display (e.g., touch screen 112).Process 700 is described below with simultaneous reference to FIG. 7 andFIGS. 8A-D. It should be appreciated that some operations in process 700can be combined, the order of some operations can be changed, and someoperations can be omitted.

At block 702 of process 700, a sequence of contact inputs can bedetected via a keyboard interface on the touch-sensitive display (e.g.,touch screen 112). The keyboard interface can be any keyboard interfacefor inputting text. For example, keyboard interface can be similar oridentical to reduced keyboard interface 600 described above withreference to FIGS. 6A-C. In some examples, the keyboard interface can bea 10-key kana keyboard interface for inputting Japanese characters. Thesequence of contact inputs can include one or more of a single-tapinput, a flick input, or a multi-tap input to one or more character keysof the keyboard interface. One or more of blocks 704-718 can beperformed in response to detecting the sequence of contact inputs atblock 702.

In examples where a flick input is used to input text (e.g., Japanesehiragana input), a contact input of the sequence of contact inputs caninclude a contact motion from a first position to a second position ofthe keyboard interface (e.g., a flick input described above withreference to FIGS. 6B-C). For example, as shown in FIG. 8A, a sequenceof contact inputs can be detected to input the string of hiraganacharacters &

(e.g., first character string 818). The sequence of contact inputs caninclude a first contact input to primary character key 802-1, a secondcontact input to primary character key 802-3, and a third contact inputto primary character key 802-4. In this example, the first contact inputand the third contact input can each be single-tap inputs. Inparticular, the first contact input and the third contact input can beintended to select primary character keys 802-1 and 802-4, respectively,on keyboard interface 800. Corresponding characters

and

can be respectively inputted as a result of the first contact input andthe third contact input. Further, the second contact input can be aflick input. In particular, with reference to FIG. 8B, the secondcontact input can be a contact motion from first position 806 to secondposition 808 on keyboard interface 800 in a direction indicated by arrow810. Second contact input can be intended to select secondary characterkey 804-1. Thus, corresponding character

can be inputted as a result of second contact input.

In flick input examples, the contact motion of second contact input caninclude various characteristics associated with the intended characterkey corresponding to the contact motion. In particular, the contactmotion can be associated with a flick distance between first position806 and second position 808 of the contact motion or a flick speed ofthe contact motion from first position 806 and second position 808.Further, the contact motion of the second contact input can beassociated with a flick angle (e.g., angle 812) with respect to areference axis (e.g., reference axis 814) of keyboard interface 800.

In examples where multi-tap input is used to input text, a contact inputof the sequence of contact inputs can include a first contact to a keyof the keyboard interface and a second contact to the key of thekeyboard interface (e.g., a double-tap input). The first contact and thesecond contact can occur within a predetermined amount of time.Additionally, the contact input can include a break in contact betweenthe first contact and the second contact. Referring back to the exampleshown in FIG. 8A, the sequence of contact inputs for inputting thestring of hiragana characters

can include a multi-tap input. Specifically, the first contact input andthe third contact input of the sequence of contact inputs can eachinclude a single-tap input to primary character keys 802-1 and 802-3,respectively. The second contact input of the sequence of contact inputscan include a first touch input to primary character key 802-3 followedby a second touch input to primary character key 802-3. First touchinput and second touch input can occur within a predetermined amount oftime. Further, a break in touch contact can occur between the firsttouch contact and the second touch contact.

In multi-tap input examples, the contact input can include variouscharacteristics for determining the character key corresponding to thecontact input. Some of these characters can be similar to those of flickinputs, such as, for example, the position of each tap input withrespect to the center position of each character key. Othercharacteristics can be different from those of flick inputs. Forexample, the first contact and the second contact of a multi-tap inputcan each be associated with a contact intensity (e.g., an intensity ofthe contact on a touch-sensitive surface) and a contact duration (e.g.,the duration of time in which each contact remains on thetouch-sensitive surface). The contact input can also include a timeinterval between the first contact and the second contact (e.g., thetime interval from when the first contact is released to when the secondcontact is initiated). The contact intensity, contact duration, and timeinterval can each be utilized to determine the character keycorresponding to the contact input.

At block 704 of process 700, a plurality of character strings thatpotentially correspond to the sequence of contact inputs can bedetermined. In particular, each contact input of the sequence of contactinputs can be interpreted as a selection of one of several possiblecharacter keys and thus can correspond to several respective characters.Returning to the example shown in FIG. 8A, the first contact input,intended to be an input to primary character key 802-1, can bedetermined to potentially be an input to one of the surrounding primarycharacter keys 802-2, 802-4, 802-5. As shown, primary character keys802-1, 802-2, 802-4, 802-5 correspond to Japanese hiragana characters

,

,

, or

, respectively, and thus first contact input can be determined tocorrespond to any one of characters

,

,

, or

. Similarly, third contact input, intended to be an input to primarycharacter key 802-4, can be determined to potentially be an input to oneof the surrounding primary character keys 802-1, 802-5, 802-7. Thus,third contact input can be determined to correspond to any one ofcharacter

,

,

, and

.

Further, second contact input, intended to be an input to secondarycharacter key 804-1, can be determined to potentially be an input toother character keys. In particular, depending on the position of theflick input, the second contact input can potentially be interpreted asa flick input to a neighboring character key. For example, secondcontact input can be determined to potentially be an input to secondarycharacter key 816-1 of FIG. 8C (e.g., character

), where the second contact input is interpreted as a flick inputinitiated at neighboring primary character key 802-2 rather than atprimary character key 802-3. Additionally, depending on the speed ordistance of the flick input, the second contact input can potentially beinterpreted as a tap input to primary character key 802-3 (e.g.,character

) rather than a flick input to primary character key 802-3 (e.g.,character

). Thus, in this example, second contact input can potentiallycorrespond to any one of characters

,

, and

.

The plurality of character strings that potentially correspond to thesequence of contact inputs can include any combination of charactersthat potentially correspond to the first, second, and third contactinputs. Specifically, in the example of FIGS. 8A-C, the plurality ofcharacter strings can include the first character string

(“asita”—meaning tomorrow) and the second character string

(“Akita”—the name of a place). The first and second character stringscan correspond to the same portion of the sequence of contact input. Inthis example, the first character string

includes the first character

that corresponds to one interpretation of the contact motion of thesecond contact input. The second character string

includes the second character

that corresponds to another interpretation of the contact motion of thesecond contact input.

In examples where multi-tap inputs are received, each multi-tap inputcan similarly correspond to two or more character keys and thus two ormore characters. For example, an intended double-tap input could beinterpreted as having fewer taps (e.g., a single-tap input) oradditional taps (e.g., a triple-tap input), depending on the duration orintensity of each tap. In addition, depending on the position of eachtap or the time interval between taps, a double-tap input could beinterpreted as two single-tap inputs to the same character key or to twodifferent character keys. Returning to the example of FIG. 8A, thesecond contact input of the sequence of contact inputs can include afirst touch input to primary character key 802-3 followed by a secondtouch input to primary character key 802-3. In this example, the secondcontact input can potentially be interpreted as corresponding to a firstpredefined input pattern (e.g., a double-tap input) to primary characterkey 802-3, which corresponds to the first character

. In addition, the second contact input can potentially be interpretedas corresponding to a second predefined input pattern (e.g., asingle-tap input) to primary character key 802-3, which corresponds tothe third character

. In this example, the plurality of character strings that potentiallycorrespond to the sequence of contact inputs can include the firstcharacter string

(“asita”—meaning tomorrow) and the third character string

(“Asada”—a family name). In this example, the first character string

includes the first character

that corresponds to one interpretation of the second contact input. Thethird character string

includes the third character

that corresponds to another interpretation of the second contact input.

Further, as described above, a double-tap input can potentially beinterpreted as two single-tap inputs to the same character key or to twodifferent character keys depending on the position of each tap or thetime interval between taps. Thus, in the present example, the secondcontact input can potentially be interpreted as corresponding to twoseparate single-tap inputs to any of primary character key 802-3 andneighboring prima character keys 802-2, and 802-6, which can correspondto, for example, the input of characters

,

,

, and

. Therefore, in this example, the plurality of character string caninclude the character strings of

,

,

, and

. It should be recognized that other character strings resulting fromother combinations of character inputs can be contemplated.

Although, in the examples described above, only some of the neighboringcharacter keys are considered to determine the plurality of characterstrings, it should be appreciated that any number of the character keys(primary or secondary) can be considered to determine the plurality ofcharacter strings.

At block 706 of process 700, a probability of each character string ofthe plurality of character strings given the sequence of contact inputscan be determined. In particular, the probability of inputting eachcharacter key associated with each character of the character stringgiven the sequence of contact inputs can be determined using one or moregeometry models. A geometry model can encode the probability ofselecting each possible character key calculated from the sequence ofcontact inputs on the keyboard interface. The probability of eachcharacter string can then be determined based on a combined probabilityof inputting each character key associated with each character of thecharacter string given the sequence of contact inputs.

In one example, with reference to the first character string

, the probability that the first contact input (e.g., a tap input) is anintended input to select primary character key 802-1 (e.g.,corresponding to the character

), the probability that the second contact input (e.g., a flick inputfrom position 806 to position 808) is an intended input to selectsecondary character key 804-1 (e.g., corresponding to the character

), and the probability that the third contact input is an intended inputto select primary character key 802-4 (e.g., corresponding to thecharacter

) can each be determined using one or more geometry models. Theprobability of the first character string

given the sequence of contact inputs can thus be determined based on acombination of each of the above determined probabilities. Theprobability of the second character string

given the sequence of contact inputs and the probability of the thirdcharacter string

given the sequence of contact inputs can be determined in a similarmanner.

The probability that a contact input is an intended input to select aparticular character key can be based on several factors associated withthe contact input. For tap inputs, such factors can include the positionof the tap input with respect to the center position of each characterkey, the intensity of the tap input, or the duration of the tap input(e.g., the duration in which contact is sustained with the keyboardinterface). In particular, a higher probability can be associated with ashorter distance between the position of the tap input and the centerposition of the particular character key, a greater intensity of the tapinput, or a longer duration of the tap input.

For flick inputs, the probability that a contact input is an intendedinput to select a particular character key can be based on similarfactors as for tap inputs, described above. Additionally, theprobability can be based on a flick input distance (e.g., a distancebetween first position 806 and second position 808 of the contact motionin FIG. 8B), a flick input speed (e.g., a speed of the contact motionfrom first position 806 to second position 808), or a flick input angle(e.g., angle 812 in FIG. 8B). In particular, a higher probability can beassociated with a longer flick distance or a slower flick speed. Withrespect to flick angle, the probability can be based on how close theflick angle corresponds to the position of a particular character key.For example, with reference to FIG. 8B, the probability that the flickinput from position 806 to position 808 is an intended input tosecondary character key 804-1 can be higher for angle 812 that is closerto 90 degrees with respect to reference axis 814 than to 0 degrees.

In some examples, a geometry model can be implemented to account for theposition of a tap input when determining the probability that a contactinput is an intended input to select a character key. In these examples,the probability mass can be distributed to each possible key based ontwo-dimensional Gaussian distributions. In particular, the probabilitythat a contact input at a position p is an intended input to a primarycharacter key k can be expressed as:

${P\left( k \middle| p \right)} = \frac{\exp \left\lbrack {- \left( \left| {p - {c(k)}} \middle| {\text{/}D} \right. \right)^{2}} \right\rbrack}{Z}$

where Z=Σk exp [−(|p−c(k)/D)²], Σk is the summation over all possibleprimary character keys, D is a constant decay factor, and c(k) is thecenter of the character key k. As evident from the above equation, theprobability that a contact input at a position p (e.g., position 801 inFIG. 8A) is an intended input to a primary character key k (e.g.,primary character key 802-1 in FIG. 8A) can be determined to be higherwhen a distance between position p and the center position of thecharacter key k(|p−c(k)|) is smaller.

Further, in some examples, a geometry model can be implemented toaccount for the flick distance and the initial position of flick inputs.In these examples, a threshold distance θ can be set on the flickdistance x, where the contact input is interpreted as a flick input(rather than a tap input) only when the flick distance is larger thanthe threshold distance θ. Additionally, the initial position p of theflick input (e.g., first position 806 in FIG. 8B) can be modeledaccording to the Gaussian distribution described above. For example,with reference to FIG. 8B, if the flick distance x (e.g., the distancebetween position 806 and position 808) is greater or equal to thethreshold distance θ, the probability that a contact input, initiated ata position p (e.g., position 806) of primary character key k₀ (e.g.,primary character key 802-3) and having a flick distance x, is anintended flick input to select secondary character key k₁ (e.g.,secondary character key 804-1) can be expressed as P(k₁|p,x)=P(k₀|p)*(G/(G+exp [−x²/E²])), and the probability that a contactinput, initiated at a position p (e.g., position 806) of primarycharacter key k₀ (e.g., primary character key 802-3) and having a flickdistance x, is an intended tap input to select primary character key k₀(e.g., primary character key 802-3) can be expressed asP(k₀|p,x)=P(k₀|P)*(exp [−x²/E²]/(G+exp [−x²/E²])), where E and G areconstants. Further, if the flick distance x (e.g., the distance betweenposition 806 and position 808) is less than the threshold distance θ,the probability that a contact input, initiated at a position p (e.g.,position 806) of primary character key k₀ (e.g., primary character key802-3) and having a flick distance x is an intended flick input toselect secondary character key k₁ (e.g., secondary character key 804-1)can be expressed as P(k₁|p, x)=P(k₀|P)*(exp [−F/x]/(H+exp [−F/x])) andthe probability that a contact input, initiated at a position p (e.g.,position 806) on primary character key k₀ (e.g., primary character key802-3) and having a flick distance x, is an intended tap input toprimary character key k₀ (e.g., primary character key 802-3) can beexpressed as P(k₀|p,x)=P(k₀|p)*(H/(H+exp [−F/x])), where F and H areconstants.

By utilizing the geometry models described above, the probability that acontact input is an intended input to select a particular character keycan be determined based on the position and/or the flick distance of thecontact input. For example, with reference to the second contact inputcomprising a contact motion from position 806 to position 808 in FIG.8B, the second contact input could be interpreted as an intended flickinput to select secondary character key 804-1, an intended flick inputto select secondary character key 816-1 (FIG. 8C), an intended tap inputto selected primary character key 802-3, or an intended tap input toselect primary character key 802-2 (FIG. 8C). Based on the position 806,the center position of primary character keys 802-2 and 802-3, and thedistance between position 806 and 808, the geometry models describedabove can be used to determine the probability that the second input isan intended input to select each of these character keys. Althoughspecific examples of geometry models are described above to account forflick distance and/or contact position, it should be recognized thatother geometry models implementing different distributions can becontemplated. Further, it should be appreciated that the other factorsdescribed above can also be modeled using one or more geometry models todetermine the probability of inputting a particular character key givena contact input. For example, factors such as contact intensity, contactduration, flick speed, or flick angle can be modeled in one or moregeometry models. Further, for multi-tap inputs, it can be contemplatedthat analogous geometry models can be implemented to account for one ormore factors such as the contact intensity of each tap, the contactposition of each tap, the contact duration of each tap, and the timeinterval between successive taps.

In some examples, a probability that a contact input of the sequence ofcontact inputs comprises a first predefined input pattern can bedetermined. For example, with reference to the first character string

, the second contact input can be a multi-tap input for inputting thecharacter

. In this example, the first predefined input pattern can comprise twosuccessive tap inputs (e.g., a first touch input followed by a secondtouch input with a break in contact in between) to primary character key802-3 and can correspond to the character

. Thus, the probability of the first character string

given the sequence of contact inputs can be determined based on theprobability that the second contact input of the sequence of contactinputs comprises the first predefined input pattern. Similarly, for thethird character string

, a probability that the second contact input of the sequence of contactinputs comprises a second predefined input pattern can be determined. Inthis example, the second predefined input pattern can comprise asingle-tap input (e.g., a first touch input followed by a break incontact) to primary character key 802-3 and can correspond to thecharacter

. Thus, the probability of the third character string

given the sequence of contact inputs can be determined based on theprobability that the second contact input of the sequence of contactinputs comprises the second predefined input pattern.

The probability that a contact input comprises a first predefined inputpattern or a second predefined input pattern can be based on severalfactors associated with the contact input. As discussed above, suchfactors can include the position of each tap input on the keyboardinterface with respect to the center position of each character key, thecontact intensity of each tap input, the contact duration of each tapinput, and the time interval between successive tap inputs of themulti-tap input. In particular, each tap input of a multi-tap input canbe detected with greater confidence with respect to a character key whenthe position of each tap is closer to the center position of thecharacter key, when the contact intensity of each tap input is greater,or when the contact duration of each time is longer. Further, twosuccessive tap inputs can be detected with greater confidence when atime interval between each tap input is greater than a lower thresholdvalue and less than an upper threshold value. It should be recognizedthat similar geometry models as described above can be implemented toaccount for one or more of these factors and the geometry model can beused to determine the probability that a contact input comprises a firstpredefined input pattern or a second predefined input pattern.

At block 708 of process 700, a first character string corresponding tothe sequence of contact inputs can be displayed in a text field on atouchscreen display (e.g., on touchscreen 112). In some examples, thefirst character string can be associated with the highest probabilityamong the plurality of character strings given the sequence of contactinputs. For example, as shown in FIG. 8B, first character string 818

is displayed on text field 820. As shown, first character string 818

includes first character 822

. As described above, first character 822

can correspond to a flick input to select secondary character key 804-1(e.g., a contact motion from position 806 to position 808 in FIG. 8B).Alternatively, first character 822

can correspond to a double-tap input to primary character key 802-3(e.g., the contact input comprising a first and a second touch contactto primary character key 802-3). In this example, first character string818

can be determined at block 706 to have the highest probability among theplurality of character strings given the sequence of contact inputs.

At block 710 of process 700, a plurality of candidate wordscorresponding to the sequence of contact inputs can be determined. Theplurality of candidate words can be determined from the plurality ofcharacter strings of block 706. In some examples, word matching withrespect to each of the plurality of character strings can be performedby searching a lexicon. A search of the lexicon can identify candidatewords that correspond to the plurality of character strings. In someimplementations, a lexicon having a trie data structure can be used toperform the word matching. In particular, an efficient stack-basedsearch algorithm can be utilized in conjunction with the trie datastructure lexicon. Such a search implementation can enable a largenumber of word matches for each computational pass through the lexicon.As such, the determining of candidate words corresponding to theplurality of character strings can be efficiently achieved with fewercomputational passes, which significantly reduces computational time andcost.

The plurality of candidate words can include words of one or morewriting systems (e.g., hiragana, katakana, or kanji). In particular, theplurality of candidate words can include words of a first writing systemand words of a second writing system. For example the first characterstring

can be determined to correspond to the candidate words

(e.g., a hiragana candidate word),

(e.g., a kanji candidate word), and

(e.g., a katakana candidate word); the second character string

can be determined to correspond to the candidate words

,

, and

; and the third character string

can be determined to correspond to the candidate words

,

, and

. As evident in this example, the sequence of contact inputs cancorrespond to a large number of candidate words that are determined frommultiple character strings. As shown in FIG. 7, block 710 can includeblocks 712-714.

At block 712 of process 700, a probability of each candidate word givena respective character string of the plurality of character strings canbe determined. For example, with reference to the first character string

, the probability of the candidate word

given the first character string

can be determined. The probability can be determined using one or morelanguage models. In particular, a language model can be trained using acorpus of text, and the probability of a candidate word given the firstcharacter string can be based on the probability of occurrence of thecandidate word in the corpus of text. Additionally or alternatively, thedetermined probability can take into account contextual information. Inparticular, the probability of each candidate word can be determinedbased on various contextual information, such as, for example, thesurrounding textual context, the type of application, the type of text,time of day or year, and the like.

In some examples, a class-based language model (e.g., class bi-gramlanguage model) can be used in conjunction with an n-gram language model(e.g., a tri-gram language model) to determine a probability of eachcandidate word given a respective character string. In particular, aclass bi-gram language model can be less computationally intensive thana tri-gram language model. Thus, an initial probability can bedetermined using a class bi-gram language model, and words having aprobability less than a threshold value can be excluded from theplurality of candidate words. The remaining candidate words can then beprocessed through a tri-gram language model to determine a finalprobability of each candidate word given a respective character string.In this way, the determination can be performed more quickly andefficiently.

At block 714 of process 700, a probability of each candidate word of theplurality of candidate words given the sequence of contact inputs can bedetermined. The probability of each candidate word given the sequence ofcontact inputs can be determined based on a combination of theprobability of each candidate word given the respective character string(e.g., determined at block 712) and the probability of the respectivecharacter string given the sequence of contact inputs (e.g., determinedat block 706). Suitable weighting factors can be applied to theprobability of each candidate word given the respective character stringand the probability of the respective character string given thesequence of contact inputs when determining the probability of eachcandidate word given the sequence of contact inputs. In someimplementations, a linear interpolation of the probability of eachcandidate word given the respective character string and the probabilityof the respective character string given the sequence of contact inputscan be performed.

Because the probability of each candidate word of the plurality ofcandidate words given the sequence of contact inputs can be determinedbased on the probability of the respective character string given thesequence of contact inputs, it should be recognized that the probabilityof each candidate word given the sequence of contact inputs can bedependent on the various factors modeled in the one or more geometrymodels described in block 706. In particular, the probability of eachcandidate word of the plurality of candidate words given the sequence ofcontact inputs can be based on factors such as the position of thecontact input with respect to the center position of each key, the flickdistance, the flick speed, the flick angle, the contact intensity, thecontact duration, and the time interval between successive tap inputs ofmulti-tap inputs.

In some examples, the plurality of candidate words can be determinedbased on the probability of each candidate word of the plurality ofcandidate words given the sequence of contact inputs. For example,candidate words having a probability less than a predetermined thresholdvalue can be excluded from the determined plurality of candidate words.

At block 716 of process 700, the plurality of candidate words of block710 can be ranked. The ranking can be performed according to theprobability of each candidate word of the plurality of candidate wordsgiven the sequence of contact inputs. In particular, the plurality ofcandidate words can be ranked from the highest probability to the lowestprobability. In one example, the first candidate words

and the second candidate words

can be ranked based on the probability of the first candidate word

given the sequence of contact inputs and the probability of the secondcandidate word

given the sequence of contact inputs, respectively. As described above,the probability of the first candidate word

given the sequence of contact inputs and the probability of the secondcandidate word

given the sequence of contact inputs can be based on the probability ofthe first character string

given the sequence of contact inputs and the probability of the secondcharacter string

given the sequence of contact inputs, respectively. In turn, theprobability of the first character string

given the sequence of contact inputs and the probability of the secondcharacter string

given the sequence of contact inputs can be based on the probabilitythat a contact input of the sequence of contact inputs is an intendedinput to select the secondary character key 804-1 (FIG. 8B) and theprobability that a contact input of the sequence of contact inputs is anintended input to select the secondary character key 816-1 (FIG. 8C),respectively.

Because the plurality of candidate words are ranked based on theprobability of each candidate word given the sequence of contact inputs,it should be recognized that the ranking can be based on the variousfactors modeled in the one or more geometry models discussed above inblock 706. In particular, the ranking can be based on factors such asthe position of the contact input with respect to the center position ofeach key, the flick distance, the flick speed, the flick angle, thecontact intensity, the contact duration, and the time interval betweensuccessive tap inputs in multi-tap inputs.

At block 718 of process 700, a portion of the plurality of candidatewords for user selection can be displayed for user selection. Thedisplayed portion can include a subset of the plurality of candidatewords that are determined and ranked at blocks 710-716. In someexamples, the portion of the plurality of candidate words can includethe top N ranked candidate words, where N is a predetermined integer.The portion of the plurality of candidate words can include a firstcandidate word and a second candidate word. The first candidate word andthe second candidate word can correspond to different character stringsthat are determined based on the sequence of contact inputs.

With reference to FIG. 8D, candidate words

,

,

,

, and

can be displayed in word selection interface 824. These candidate wordscan be the candidate words with the four highest probabilities among aplurality of determined candidate words given the sequence of inputs. Inparticular, a user can select one of the displayed candidate words viaword selection interface 824 to input the respective candidate word. Asshown, the displayed candidate words include first candidate word 826

, second candidate word 828

, and third candidate word 830

. Notably, in this example, the displayed candidate words include wordsthat are determined from different character strings. In particular, asdescribed above, first candidate word 826

, second candidate word 828

, and third candidate word 830

can be determined based on the first character string

, the second character string

, and the third character string

, respectively. Each of these character strings can be determined byconsidering various possible intended inputs corresponding to eachcontact input of the sequence of contact inputs. Thus, in contrast tolanguage input methods that determine candidate words based only asingle character string (e.g., first character string

), process 700 can determine a larger range of candidate words based onvarious probable character strings that correspond to the sequence ofcontact inputs. In this way, words that better correspond to the user'sintent can be displayed for user selection. Further, the process cancorrect for unintended contact inputs (e.g., typos) by determining anddisplaying candidate words corresponding to potentially intended contactinputs.

Although, in the above examples, process 700 is described with respectto a Japanese kana keyboard, Japanese hiragana character strings, andJapanese candidate word strings (e.g., hiragana, katakana, and kanjiwords), it should be recognized that process 700 can also be practicedusing other keyboard interfaces and writing systems (e.g., Chinese,Korean, etc.). Further, it can be contemplated that process 700 can beimplemented for inputting text of one language and obtaining atranslation of the text in another language.

4. Exemplary Electronic Devices

In accordance with some embodiments, FIG. 9 shows an exemplaryfunctional block diagram of an electronic device 900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 900 are configured to perform the techniques described above. Thefunctional blocks of the device 900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 9 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 9, an electronic device 900 includes a display unit 902configured to display a graphic user interface (e.g., a text field, wordselection interface, keyboard interface, etc.), optionally, atouch-sensitive surface unit 904 configured to receive contacts, and aprocessing unit 906 coupled to the display unit 902 and, optionally, thetouch-sensitive surface unit 904. In some embodiments, the display unit902 and the touch-sensitive surface unit 904 can be a single unit (e.g.,a touch-sensitive display unit). In some embodiments, the processingunit 906 includes a detecting unit 908, a determining unit 910, aranking unit 912, and a displaying unit 914.

The processing unit 906 is configured to detect (e.g., with detectingunit) a sequence of contact inputs via a keyboard interface on thedisplay unit 902 and/or the touch-sensitive surface unit 904. A contactinput of the sequence of contact inputs comprises a contact motion froma first position to a second position of the keyboard interface. Theprocessing unit 906 is further configured to determine (e.g., withdetermining unit 910) a plurality of candidate words corresponding tothe sequence of contact inputs. The processing unit 906 is furtherconfigured to rank (e.g., with ranking unit 912) the plurality ofcandidate words based on a probability that the contact input is anintended input to a first key of the keyboard interface, and aprobability that the contact input is an intended input to a second keyof the keyboard interface. The processing unit 906 is further configuredto display (e.g., with displaying unit), via display unit 902, a portionof the plurality of candidate words for user selection.

In some embodiments, the first key corresponds to a first writing symbolof a language and the second key corresponds to a second writing symbolof the language. In some embodiments, the plurality of candidate wordsincludes words of a first writing system and words of a second writingsystem.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a plurality of characterstrings that potentially correspond to the sequence of contact inputs.The processing unit 906 is further configured to determine (e.g., withdetermining unit 910) using a geometry model, a probability of eachcharacter string of the plurality of character strings given thesequence of contact inputs, where the plurality of candidate words isdetermined from the plurality of character strings based on theprobability of each character string of the plurality of characterstrings given the sequence of contact inputs.

In some embodiments, the plurality of candidate words are determinedbased on a lexicon of a language model. In some embodiments, theprobability that the contact input is an intended input to the first keyof the keyboard interface is determined based on a distance between thefirst position and a center position of the first key, and theprobability that the contact input is an intended input to the secondkey of the keyboard interface is determined based on a distance betweenthe first position and a center position of the second key.

In some embodiments, the probability that the contact input is anintended input to the first key of the keyboard interface and theprobability that the contact input is an intended input to the secondkey of the keyboard interface are each determined based on a distancebetween the first position and the second position of the contactmotion.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a probability of eachcandidate word given the sequence of contact inputs, where ranking theplurality of candidate words is based on the probability of eachcandidate word given the sequence of contact inputs.

In some embodiments, the probability of each candidate word of theplurality of candidate words given the sequence of contact inputs isdetermined based on a probability of a respective character string ofthe plurality of character strings given the sequence of contact inputs.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a probability of eachcandidate word of the plurality of candidate words given a respectivecharacter string of the plurality of character strings, where theprobability of each candidate word of the plurality of candidate wordsgiven the sequence of contact inputs is determined based on theprobability of each candidate word of the plurality of candidate wordsgiven a respective character string of the plurality of characterstrings.

In some embodiments, the probability of each candidate word of theplurality of candidate words given a respective character string of theplurality of character strings is determined using one or more languagemodels.

In some embodiments, the plurality of candidate words is determinedusing a lexicon with a trie data structure.

In some embodiments, the plurality of candidate words is ranked based ona distance between the first position and a center position of each keyon the keyboard interface. In some embodiments, the plurality ofcandidate words is ranked based on a distance between the first positionand the second position of the contact motion. In some embodiments, theplurality of candidate words is ranked based on a speed of the contactmotion from the first position and the second position. In someembodiments, the plurality of candidate words is ranked based on anangle of the contact motion with respect to a reference axis of thekeyboard interface. In some embodiments, the keyboard interface is a10-key kana keyboard interface.

In some embodiments, the processing unit 906 is configured to detect(e.g., with detecting unit) a sequence of contact inputs via a keyboardinterface on the display unit 902 and/or the touch-sensitive surfaceunit 904. A contact input of the sequence of contact inputs comprises acontact motion from a first position to a second position of thekeyboard interface. The processing unit 906 is further configured todisplay (e.g., with displaying unit 914) in a text field via the displayunit 902, a first character string corresponding to the sequence ofcontact inputs. The first character string includes a first characterthat corresponds to the contact motion. The processing unit 906 isfurther configured to determine (e.g., with determining unit 910) aplurality of candidate words corresponding to the sequence of contactinputs. The plurality of candidate words includes a first candidate wordand a second candidate word. The first candidate word is based on thefirst character string and the second candidate word is based on asecond character string that corresponds to the sequence of contactinputs. The second character string includes a second charactercorresponding to the contact motion. The processing unit 906 is furtherconfigured to display (e.g., with displaying unit 914), via the displayunit 902, a portion of the plurality of candidate words for userselection. The portion includes the first candidate word and the secondcandidate word.

In some embodiments, the first character corresponds to a first key ofthe keyboard interface, and the second character corresponds to a secondkey of the keyboard interface that is different from the first key. Insome embodiments, the first character string and the second characterstring each include characters of a first writing system and theplurality of candidate words includes words of a first writing systemand words of a second writing system.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a plurality of characterstrings corresponding to the sequence of contact inputs, where theplurality of character strings includes the first character string andthe second character string. The processing unit 906 is furtherconfigured to determine (e.g., with determining unit 910), using ageometry model, a probability of each character string of the pluralityof character strings given the sequence of contact inputs, where theplurality of candidate words is determined based on the probability ofeach character string of the plurality of character strings given thesequence of contact inputs.

In some embodiments, the probability of each character string of theplurality of character strings given the sequence of contact inputs isdetermined based on a distance between the first position and a centerposition of each key on the keyboard interface. In some embodiments, theprobability of each character string of the plurality of characterstrings given the sequence of contact inputs is determined based on adistance between the first position and the second position of thecontact motion.

In some embodiments, the probability of each character string of theplurality of character strings given the sequence of contact inputs isdetermined based on a speed of the contact motion from the firstposition and a second position. In some embodiments, the probability ofeach character string of the plurality of character strings given thesequence of contact inputs is determined based on an angle of thecontact motion with respect to a reference axis of the keyboardinterface.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a probability of eachcandidate word of the plurality of candidate words given a respectivecharacter string of the plurality of character strings, where theplurality of candidate words is determined based on the probability ofeach candidate word of the plurality of candidate words given arespective character string of the plurality of character strings.

In some embodiments, the plurality of candidate words is determinedusing a lexicon with a trie data structure. In some embodiments, thekeyboard interface is a 10-key kana keyboard interface.

In some embodiments, the processing unit 906 is configured to detect(e.g., with detecting unit) a sequence of contact inputs via a keyboardinterface on the display unit 902 and/or touch-sensitive surface unit904). A contact input of the sequence of contact inputs comprises afirst contact to a key of the keyboard interface and a second contact tothe key of the keyboard interface. The processing unit 906 is furtherconfigured to display (e.g., with displaying unit 914), in a text fieldon the display unit 902, a first character string corresponding to thesequence of contact inputs, where the first character string includes afirst character that corresponds to the contact input. The processingunit 906 is further configured to determined (e.g., with determiningunit 910) a plurality of candidate words corresponding to the sequenceof contact inputs. The plurality of candidate words includes a firstcandidate word and a second candidate word, where the first candidateword is based on the first character string and the second candidateword is based on a second character string that corresponds to thesequence of contact inputs. The second character string includes asecond character corresponding to the contact input. The processing unit906 is further configured to display (e.g., with displaying unit 914),via the display unit 902, a portion of the plurality of candidate wordsfor user selection. The portion includes the first candidate word andthe second candidate word.

In some embodiments, the contact input further comprises a break incontact between the first contact and the second contact. In someembodiments, the first character string and the second character stringeach include characters of a first writing system, and the plurality ofcandidate words includes words of a first writing system and words of asecond writing system.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a plurality of characterstrings that potentially correspond to the sequence of contact inputs,the plurality of character strings include the first character stringand the second character string. The processing unit 906 is furtherconfigured to determine (e.g., with determining unit 910), using ageometry model, a probability of each character string of the pluralityof character strings given the sequence of contact input, where theplurality of candidate words is determined based on the probability ofeach character string of the plurality of character strings given thesequence of contact input.

In some embodiments, the first character corresponds to a firstpredefined input pattern to the key of the keyboard interface, and thesecond character corresponds to a second predefined input pattern to thekey of the keyboard interface.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a probability that thecontact input comprises the second predefined input pattern, wherein theprobability of each character string of the plurality of characterstrings given the sequence of contact input is determined based on theprobability that the contact input comprises the second predefined inputpattern.

In some embodiments, the probability that the contact input comprisesthe second predefined input pattern is determined based on an intensityof the first contact or the second contact. In some embodiments, theprobability that the contact input comprises the second predefined inputpattern is determined based on a duration of the first contact or thesecond contact. In some embodiments, the probability that the contactinput comprises the second predefined input pattern is determined basedon a distance between a center position of the key and a position of thefirst contact or the second contact. In some embodiments, theprobability that the contact input comprises the second predefined inputpattern is determined based on a time interval between the first contactand the second contact.

In some embodiments, the processing unit 906 is further configured todetermine (e.g., with determining unit 910) a probability of eachcandidate word of the plurality of candidate words given a respectivecharacter string of the plurality of character strings, where theplurality of candidate words is determined based on the probability ofeach candidate word of the plurality of candidate words given arespective character string of the plurality of character strings.

In some embodiments, the plurality of candidate words is determinedusing a lexicon with a trie data structure. In some embodiments, thekeyboard interface is a 10-key kana keyboard interface.

The operations described above with reference to FIG. 7 are, optionally,implemented by components depicted in FIGS. 1A-1B or FIG. 9. Forexample, detecting operation 702, determining operations 704, 706, 710,712, 714, ranking operation 716, and displaying operations 708, 718 maybe implemented by text input module 134. Text input module 134 candetect a sequence of contact inputs via a keyboard interface displayedon touch-sensitive display 112. Text input module 134 can determine aplurality of character strings potentially corresponding to the sequenceof contact inputs. Text input module 134 can determine (e.g., with ageometry model of the text input module 134) a probability of eachcharacter string given the sequence of contact inputs. Text input module134 can display a first character string of the plurality of characterstrings in a text field displayed on touch-sensitive display 112. Textinput module 134 can determine a plurality of candidate wordscorresponding to the sequence of contact inputs. Text input module 134can determine (e.g., with a language model of the text input module 134)a probability of each candidate word given a respective character stringof the plurality of character strings. Text input module 134 candetermine a probability of each candidate word given the sequence ofcontact inputs. Text input module 134 can rank the plurality ofcandidate words based on a probability that the contact input is anintended input to a first key of the keyboard interface, and aprobability that the contact input is an intended input to a second keyof the keyboard interface. Text input module 134 can display ontouch-sensitive display 112 a portion of the plurality of candidatewords for user selection. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A method for inputting language, the methodcomprising: at a device having one or more processors, memory, and atouch-sensitive display: detecting a sequence of contact inputs via akeyboard interface on the touch-sensitive display, wherein a contactinput of the sequence of contact inputs comprises a contact motion froma first position to a second position of the keyboard interface;determining a plurality of candidate words corresponding to the sequenceof contact inputs; ranking the plurality of candidate words based on aprobability that the contact input is an intended input to select afirst key of the keyboard interface, and a probability that the contactinput is an intended input to select a second key of the keyboardinterface; and displaying a portion of the plurality of candidate wordsfor user selection.
 2. The method of claim 1, wherein the first keycorresponds to a first writing symbol of a language and the second keycorresponds to a second writing symbol of the language.
 3. The method ofclaim 1, wherein the plurality of candidate words includes words of afirst writing system and words of a second writing system.
 4. The methodof claim 1, further comprising: determining a plurality of characterstrings that potentially correspond to the sequence of contact inputs;and determining, using a geometry model, a probability of each characterstring of the plurality of character strings given the sequence ofcontact inputs, wherein the plurality of candidate words is determinedfrom the plurality of character strings based on the probability of eachcharacter string of the plurality of character strings given thesequence of contact inputs.
 5. The method of claim 1, wherein theplurality of candidate words are determined based on a lexicon of alanguage model.
 6. The method of claim 1, wherein: the probability thatthe contact input is an intended input to select the first key of thekeyboard interface is determined based on a distance between the firstposition and a center position of the first key; and the probabilitythat the contact input is an intended input to select the second key ofthe keyboard interface is determined based on a distance between thefirst position and a center position of the second key.
 7. The method ofclaim 1, wherein the probability that the contact input is an intendedinput to select the first key of the keyboard interface and theprobability that the contact input is an intended input to select thesecond key of the keyboard interface are each determined based on adistance between the first position and the second position of thecontact motion.
 8. The method of claim 1, further comprising:determining a probability of each candidate word given the sequence ofcontact inputs, wherein ranking the plurality of candidate words isbased on the probability of each candidate word given the sequence ofcontact inputs.
 9. The method of claim 8, wherein the probability ofeach candidate word of the plurality of candidate words given thesequence of contact inputs is determined based on a probability of arespective character string of the plurality of character strings giventhe sequence of contact inputs.
 10. The method of claim 8, furthercomprising: determining a probability of each candidate word of theplurality of candidate words given a respective character string of theplurality of character strings, wherein the probability of eachcandidate word of the plurality of candidate words given the sequence ofcontact inputs is determined based on the probability of each candidateword of the plurality of candidate words given a respective characterstring of the plurality of character strings.
 11. The method of claim10, wherein the probability of each candidate word of the plurality ofcandidate words given a respective character string of the plurality ofcharacter strings is determined using one or more language models. 12.The method of claim 1, wherein the plurality of candidate words isdetermined using a lexicon with a trie data structure.
 13. The method ofclaim 1, wherein the plurality of candidate words is ranked based on adistance between the first position and a center position of each key onthe keyboard interface.
 14. The method of claim 1, wherein the pluralityof candidate words is ranked based on a distance between the firstposition and the second position of the contact motion.
 15. The methodof claim 1, wherein the plurality of candidate words is ranked based ona speed of the contact motion from the first position and the secondposition.
 16. The method of claim 1, wherein the plurality of candidatewords is ranked based on an angle of the contact motion with respect toa reference axis of the keyboard interface.
 17. The method of claim 1,wherein the keyboard interface is a 10-key kana keyboard interface. 18.A non-transitory computer-readable storage medium comprisingcomputer-executable instructions, which when executed by one or moreprocessors, cause the one or more processors to: detect a sequence ofcontact inputs via a keyboard interface on the touch-sensitive display,wherein a contact input of the sequence of contact inputs comprises acontact motion from a first position to a second position of thekeyboard interface; determine a plurality of candidate wordscorresponding to the sequence of contact inputs; rank the plurality ofcandidate words based on a probability that the contact input is anintended input to select a first key of the keyboard interface, and aprobability that the contact input is an intended input to select asecond key of the keyboard interface; and display a portion of theplurality of candidate words for user selection.
 19. A systemcomprising: one or more processors; memory storing computer-readableinstructions, which when executed by the one or more processors, causethe one or more processors to: detect a sequence of contact inputs via akeyboard interface on the touch-sensitive display, wherein a contactinput of the sequence of contact inputs comprises a contact motion froma first position to a second position of the keyboard interface;determine a plurality of candidate words corresponding to the sequenceof contact inputs; rank the plurality of candidate words based on aprobability that the contact input is an intended input to select afirst key of the keyboard interface, and a probability that the contactinput is an intended input to select a second key of the keyboardinterface; and display a portion of the plurality of candidate words foruser selection.
 20. The system of claim 19, wherein thecomputer-readable instructions further cause the one or more processorsto: determine a plurality of character strings that potentiallycorrespond to the sequence of contact inputs; and determine, using ageometry model, a probability of each character string of the pluralityof character strings given the sequence of contact inputs, wherein theplurality of candidate words is determined from the plurality ofcharacter strings based on the probability of each character string ofthe plurality of character strings given the sequence of contact inputs.21. The system of claim 19, wherein: the probability that the contactinput is an intended input to select the first key of the keyboardinterface is determined based on a distance between the first positionand a center position of the first key; and the probability that thecontact input is an intended input to select the second key of thekeyboard interface is determined based on a distance between the firstposition and a center position of the second key.
 22. The system ofclaim 19, wherein the probability that the contact input is an intendedinput to select the first key of the keyboard interface and theprobability that the contact input is an intended input to select thesecond key of the keyboard interface are each determined based on adistance between the first position and the second position of thecontact motion.
 23. The system of claim 19, wherein thecomputer-readable instructions further cause the one or more processorsto: determine a probability of each candidate word given the sequence ofcontact inputs, wherein ranking the plurality of candidate words isbased on the probability of each candidate word given the sequence ofcontact inputs.
 24. The system of claim 23, wherein the probability ofeach candidate word of the plurality of candidate words given thesequence of contact inputs is determined based on a probability of arespective character string of the plurality of character strings giventhe sequence of contact inputs.
 25. The system of claim 23, wherein thecomputer-readable instructions further cause the one or more processorsto: determine a probability of each candidate word of the plurality ofcandidate words given a respective character string of the plurality ofcharacter strings, wherein the probability of each candidate word of theplurality of candidate words given the sequence of contact inputs isdetermined based on the probability of each candidate word of theplurality of candidate words given a respective character string of theplurality of character strings.